[Back]

Rhapsody Developer Release Copyright 1998 by Apple Computer, Inc. All Rights Reserved.

Rhapsody Developer Release Notes:
Java AWT

This file contains release notes for the Developer Release (2) of the Java Abstract Window Toolkit (AWT). The AWT provides platform-independent graphical user-interface services for applications written in Java. This is the first release of the AWT for Rhapsody; it is based on the JDKTM 1.1 from Sun Microsystems.

 

Notes Specific to Developer Release

Known Problems

These bugs are known to exist in the Developer Release of the AWT:

Reference

2001774

Problem

Scroll bar knob sometimes appears when it shouldn't.

Description

When a scroll bar is first created, the scroll knob is visible even if there aren't enough items to require scrolling. Once there are enough items to require scrolling, then the knob will become the correct size, and it disappears if the number of items again becomes too small to require scrolling.

Workaround

Add enough items to force scrolling, and then remove them.

Reference

2005449

Problem

Scroll bars do not scale width.

Description

The AWT allows scroll bars of varying width (for vertical scrollers) or height (for horizontal scrollers), but the native Yellow Box does not yet support this capability. Scroll bars wider than 16 pixels still appear 16 pixels wide, while scroll bars narrower than 16 pixels are clipped to the correct width without scaling the appearance. In either case, the scroll bars are fully functional.

Workaround

Use scroll bars with the default width.

Reference

2206659

Problem

Scaled, transparent images draw incorrectly.

Description

When the AWT draws an image that contains transparent pixels with a scaling factor, the transparent pixels do not draw properly if you are drawing to an off-screen buffer first. The transparent pixels remain transparent all the way to the screen, so they do not overwrite the current screen pixels with the pixel values from the off-screen buffer.

Workaround

Draw the transparent image to an offscreen buffer without scaling, then scale it in a separate operation.

Reference

2210911, 2210912

Problem

Applets cannot be restarted reliably.

Description

The Restart menu command in the appletviewer tool does not reliably reinitialize applets. Some applets behave properly, but others may restart with incorrect state or may throw an exception.

Workaround

Use the Reload menu command instead.

Reference

2210936, 2224070

Problem

Java process can occasionally hang when threads are terminated.

Description

A small number of cases have been found in which a deadlock occurs after a thread is terminated with Thread.stop(). The problem is that an internal lock is still held by the terminated thread, so no other thread can acquire the lock. Sun is deprecating Thread.stop() in the JDK 1.2 to avoid this kind of problem.

Workaround

Don't use Thread.stop(). Enter the following URL in a web browser to see a discussion of alternative techniques for terminating a thread:

http://www.javasoft.com/products/jdk/1.2/docs/guide/misc/threadPrimitiveDeprecation.html